

README file for:   Nortel Zoe Code Release 1.0.1.6


*** WARNING *** WARNING *** WARNING ***
***
*** Before you download this image to the switch, please ensure you have
*** performed the
***
***       "NORTEL ZOE PROGRAMMABLE HARDWARE UPGRADE - V1.0"
***
*** available on OSS.
***
*** WARNING *** WARNING *** WARNING ***


*** IMPORTANT *** IMPORTANT *** IMPORTANT ***
***
*** SEE SPECIAL UPGRADE PROCEDURE BELOW IF YOU ARE UPGRADING
*** FROM RELEASE 0.0.0 (the original ship level).
***
*** NOTE: To determine the software version, execute the following command at
***       the  switch CLI prompt (after step 3c, below):
***
***       /info/sys/gen
***
*** A version incompatibility issue was discovered that could cause the Boot
*** image flash process to hang and therefore corrupt the boot code, rendering
*** the switch unuseable.
***
*** IMPORTANT *** IMPORTANT *** IMPORTANT ***


CONTENTS:
---------

1) New Features Supported / Major Bug Fixes

2) TFTP Upgrade Procedures

3) How to check Software Revision levels


----------------------------------------
New Features Supported / Major Bug Fixes
----------------------------------------

- S/W component versions:

      GbE Boot  - 1.0.1.6
      GbE OS    - 1.0.1.6

Fix description for 1.0.1.2 thru 1.0.1.6 follow:

Change logs for 1.0.1.6
------------------------------------------------------------------
CR NUMBER: Q01131183
  
SUBMIT DESCRIPTION:
no tagged PVST BPDUs in the native vlan if associated STP off

SUBMIT DESCRIPTION:
Return port alias for ZOE ifDesc.


1.0.1.5 fixes: 
------------------------------------------------------------------
  CR NUMBER: Q01119330
    SUBMIT DESCRIPTION:
     backward port from ZOE 1.X
     - flood Cisco's BPDU for ports that are STP disabled
   
    CR NUMBER:  Q01109930 
  SUBMIT DESCRIPTION:
  - Bearstearns fix for igmp not working until /cfg/l3 menu toggle.
  
  CR NUMBER: Q01123406
  SUBMIT DESCRIPTION:
  Fixed 050418. Display INT,MGMT,EXT for ZOE ports. Return  up/down for port state. 
  Removed dormant for port state.
  
====================================================================== 
NOTE: EVERYTHING BELOW THIS LINE WAS ALREADY VERIFIED BY NORTEL SQA 
with 2 WEEKS OF VERIFICATION/REGRESSION back in JAN
========================================================================


 1.0.1.4 fixes: 
------------------------------------------------------------------
  
  CR NUMBER: Q01054973
  SUBMIT DESCRIPTION:
  MSTP_RSTP_ALTEON: in rstp mode, if trunking link down,
  need to get stp state correctly to flush fdb.
  
  
  CR NUMBER: Q01069918
    SUBMIT DESCRIPTION:
  - Remove check for static mrouter port to be of server port type
    on static mrouter port deletion.
  

  CR NUMBER: Q01091884 
   DESCRIPTION:	 ZOE 1.0.1.1 CLI misreporting high MP utilization

1.0.1.3 fixes: 
------------------------------------------------------------------

  
  CR NUMBER: Q01069036, Q01054973
    SUBMIT DESCRIPTION:
    - Add more fixes to the previous checkin: when flush L2 entries by port and 
  if the port is trunk port then we need to flush L2 entries by trunk id. 
  Similarly, when flushing L2 entries by port and vlan then we need to purge
  L2 entries by trunk id and vlan.  The flushing for trunk happens only if the
  trunk is down. 
  - The trunk is down when one of the following condition met: 
    1. The STP states of all trunk members are in either blocking or disabled
      mode.
      There are two cases in this part:
      .  At the time flushing L2, if the vlan is known, then we check
         the STP states of all trunk members in the specified vid.
      .  If the vid is unknown when flushing L2, we determine the trunk down
         if all trunk members are in blocking/disabled in any one vlan that the
         trunk belongs to.
    2. The links of all trunk members are down.  This is done simply by
       checking the stp_trunk_port[trunk_id].
  
   
  
  CR NUMBER: Q01031976.   
  SUBMIT DESCRIPTION:
   Showed correct VRRP router info in the dashboard.
  
  
1.0.1.2 fixes: 
------------------------------------------------------------------
  
  CR NUMBER: Q01048806  
  SUBMIT DESCRIPTION: Fixed problem in BBI config. for link type for STP port config.


-----------------------
TFTP Upgrade Procedures
-----------------------

*** IMPORTANT *** IMPORTANT *** IMPORTANT ***
***
*** SEE SPECIAL UPGRADE PROCEDURE BELOW IF YOU ARE UPGRADING
*** FROM RELEASE 0.0.0 (the original ship level).
***
*** NOTE: To determine the software version, execute the following command at
***       the  switch CLI prompt (after step 3c, below):
***
***       /info/sys/gen
***
*** A version incompatibility issue was discovered that could cause the Boot
*** image flash process to hang and therefore corrupt the boot code, rendering
*** the switch unuseable.
***
*** IMPORTANT *** IMPORTANT *** IMPORTANT ***


1. Place the Boot (1.0.1.6_Boot.img) and OS (1.0.1.6_OS.img) image files
   into a directory on the TFTP server.  Enable the server and set its default
   directory to the one where the image files reside.


2. Establish a physical connection between the ethernet port of the BladeCenter
   Management Module and the TFTP Server.


3. In order to transfer the image files from the TFTP Server to the switch a
   telnet session via the Management Module can be used.

   a) Using the Management Module GUI, configure the IP Addr/Mask of the
      Management Module External (eth0) and Internal (eth1) interfaces, the Zoe
      switch and the TFTP server so that they all reside on the same subnet.

      For example,

          Management Module (eth0 I/F) => 192.168.70.125 / 255.255.255.0

          Management Module (eth1 I/F) => 192.168.70.126 / 255.255.255.0
 
          Zoe Switch Current IP Config => 192.168.70.127 / 255.255.255.0

          TFTP Server                  => 192.168.70.254 / 255.255.255.0

      NOTE: Although configured as such, for this example, the TFTP Server does
            not have to be on the same subnet as long as a proper gateway address
            is configured in the switch.

   b) Using the Management Module GUI, navigate to:

       I/O Module Tasks --> Management --> Bay X --> Start Telnet session
    
      When the telnet session is established, you will begin using the Command
      Line Interface (CLI) of the Zoe switch.

   c) Enter "admin" for the password and 'n' if asked about setup.


   NOTES: 
        - An FTP server, instead of TFTP, can be used to facilitate the upgrade.

        - Upgrades can also be performed using external ports. Please see
          "Externally managing the GbE switch module" on p.31 in the Installation
          Guide. The guide is located at the following link:

          ftp://ftp.software.ibm.com/pc/pccbbs/pc_servers_pdf/13n0316.pdf


4. The Zoe switch provides storage (banks) for two (2) OS images and one (1) Boot
   image. What you are about to do consists of the following sequence:

   - load the new OS image into one of the image banks
   - reset the switch
   - load the Boot image
   - reset the switch

   NOTE: When you reset the switch it boots using the 'selected' image (1 or 2).
         Please ensure that you are booting from the upgraded image
         (execute /boot/cur at the CLI prompt to determine).

                                                                                                             
   *** IMPORTANT *** IMPORTANT *** IMPORTANT ***
   ***
   *** WHEN UPGRADING FROM 0.0.0 you MUST, repeat MUST, install the new OS
   *** image file into Image Bank #1 and then reset the switch.
   *** 
   *** After the upgrade (and before the reset), execute the /boot/cur command
   *** at the CLI prompt to MAKE ABSOLUTELY SURE that the switch reflects that
   *** it is "Currently set to boot software image1..." AND that the Current FLASH
   *** software for image1 is "version 1.0.1.6".
   ***
   *** It is EXTREMELY IMPORTANT that you DO NOT load the OS into Image Bank #2
   *** and DO NOT attempt to upgrade the Boot image until AFTER you have successfully
   *** loaded the new OS image (into bank 1) and reset the switch.
   ***
   *** NOT following this procedure can result in your switch becoming unuseable.
   *** If that happens, your only recourse will be to send it back for repair.
   ***
   *** IMPORTANT *** IMPORTANT *** IMPORTANT ***


   To upgrade Zoe, enter the following commands using the CLI:

     /boot/gtimg X TADDR 1.0.1.6_OS.img <enter>
                                                        
      -Execute Step 5 (below)-

       NOTE: Resetting the switch kicks you out of the CLI, so you'll need to 
             execute Steps 3b and 3c (above) again before entering the next
             command.


     /boot/gtimg boot TADDR 1.0.1.6_Boot.img <enter>

      -Execute Step 5 (below)-

    WHERE:
    ------
    TADDR  => IP Address of the TFTP Server
    imageX => X= 1 or 2 (depends which image bank you want to use)
 
        NOTE: The recommendation is that you retain the previous OS release in
              whichever image bank it was, load the upgrade into the other
              bank and then boot from that image bank (use /boot/image command
              to select the appropriate image to boot from).


5.  You MUST Reset the switch to activate the new image(s):

    Using the Management Module GUI, navigate to:
    
        I/O Module Tasks --> Power/Restart

    Select the appropriate Switch Bay then click ...

        RESTART MODULE AND RUN STANDARD DIAGNOSTICS

    Alternately, you can simply unplug and replug the switch module.

    Wait for about 60 seconds for POST to complete successfully.

    NOTE: Resetting the switch kicks you out of the CLI, so you'll need to 
          execute again Steps 3b and 3c (above) to enter more CLI commands.



How to check Software Revision levels
-------------------------------------

1.  Using the Management Module GUI, navigate to:
    
       Management Module --> VPD Firmware

    Scroll down to view the VPD info for the correct Zoe Switch.
    You should see the following entries:


    FIRMWARE TYPE              BUILD ID       RELEASED       REVISION
    -------------              --------       --------       --------

     Boot ROM                  WMZ01001       12/14/2004      0100
     Main Application 1(or 2)  WMZ01001       12/14/2004      0100

    
    Note: If you upgraded the new OS using image 1 then "WMZ01001 ..."
          will show up on the "Main Application 1" line.  Otherwise, it will
          be displayed on the "Main Application 2" line.


